Skip to content

AP-513 improving order of operations#21

Merged
jason-raitz merged 3 commits intomainfrom
AP-513_log_tracing_part_deux
Feb 18, 2026
Merged

AP-513 improving order of operations#21
jason-raitz merged 3 commits intomainfrom
AP-513_log_tracing_part_deux

Conversation

@jason-raitz
Copy link
Contributor

  • co-authored with @danschmidt5189
  • some logs were still not getting request_id logged
  • we believe there an issue with when the two around_performs were called
  • this commit should eliminate that problem

Copy link
Member

@danschmidt5189 danschmidt5189 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Curious about the test failures.

@jason-raitz jason-raitz marked this pull request as ready for review February 17, 2026 16:39
Copy link
Member

@awilfox awilfox left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is good, but I am a bit concerned that the mutation of arguments is done in a method. If we change how or when (or if) that method is called, suddenly the arguments will change too. I think it's better to do this in a dedicated callback, i.e. before_perform :set_request_id or something.

Copy link
Member

@anarchivist anarchivist left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good. one clarificatory question about your docs in comments, but otherwise r+.

edit: this might be related to @awilfox's concern, too.

@jason-raitz
Copy link
Contributor Author

This is good, but I am a bit concerned that the mutation of arguments is done in a method. If we change how or when (or if) that method is called, suddenly the arguments will change too. I think it's better to do this in a dedicated callback, i.e. before_perform :set_request_id or something.

I think you're right. I'll redo it. I think the reason some of the jobs are not getting the request_id right now is possibly because of multiple before_performs and around_performs making it a race condition? I'll try something different in a bit.

@jason-raitz jason-raitz marked this pull request as draft February 17, 2026 20:14
@jason-raitz jason-raitz marked this pull request as ready for review February 17, 2026 21:53
Copy link
Member

@anarchivist anarchivist left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👏 i like the direction this took! r+.

Copy link
Member

@danschmidt5189 danschmidt5189 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, I like how this turned out, very clean / Rails-y.

Copy link
Member

@awilfox awilfox left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great. Thanks for cleaning it up so well! r+

- co-authored with @danschmidt5189
- some logs were still not getting request_id logged
- we believe there an issue with when the two around_performs were
  called
- this commit should eliminate that problem
- replaces the positional removal with a destructuring and reassignment.
@jason-raitz jason-raitz force-pushed the AP-513_log_tracing_part_deux branch from 68e4764 to 2ce1587 Compare February 18, 2026 16:01
@jason-raitz jason-raitz merged commit eab0984 into main Feb 18, 2026
5 checks passed
@jason-raitz jason-raitz deleted the AP-513_log_tracing_part_deux branch February 18, 2026 16:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants